Problem

Running cm:stacks:clone while unauthenticated produced no output at all when showConsoleLogs was false (the default after config:set:log --level info).

Expected: ERROR: Please login to execute this command, csdx auth:login
Actual: Silent exit — user has no idea why the command stopped

Root Cause

Two compounding issues in run():

1. progressSupportedModule was set unconditionally at the top of run()

// ❌ Before — ran before any auth check
configHandler.set('log.progressSupportedModule', 'clone');

clone is in PROGRESS_SUPPORTED_MODULES, so setting this put the logger into "progress-bar mode" where showConsoleLogs defaults to false. The Console transport was never added to the winston logger, so log.error(...) only wrote to the log file.

2. Stale value persisted across CLI invocations
configHandler.set writes to an encrypted config file on disk. Once set by any run, the value persisted for all subsequent runs — meaning even commands that never called handleClone() (i.e. auth failures) still started with progressSupportedModule: 'clone' from disk, silencing their error output.

Fix

src/commands/cm/stacks/clone.ts

• Clear progressSupportedModule to null at the very start of run() — before parse() or any log call — so a fresh logger instance is created without progress-bar mode active.
• Re-set it to 'clone' as the first line of handleClone() — so progress-bar mode only activates after authentication passes and the actual clone operation begins.

async run(): Promise<void> {
  try {
    // Clear stale value from previous runs — ensures auth errors always reach console
    configHandler.set('log.progressSupportedModule', null);  // ← NEW
    const { flags } = await self.parse(StackCloneCommand);

    const handleClone = async () => {
      configHandler.set('log.progressSupportedModule', 'clone');  // ← MOVED here
      ...
    };

    if (isAuthenticated()) {
      handleClone();
    } else {
      log.error('Please login...');  // ← now always visible
    }
  }
}

Changes

Test Updates

Behaviour